Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the code that extends the prediction to Renderer #1562

Merged
merged 8 commits into from
Sep 21, 2017

Conversation

pleroy
Copy link
Member

@pleroy pleroy commented Sep 17, 2017

This was noticed when investigating #1561 (the new test show a case where we evaluate the prediction after its last point) but this is really unrelated because #1561 is about evaluating the prediction before its first point.

Also making Vessel::UpdatePrediction idempotent for performance.

@eggrobin eggrobin added LGTM and removed LGTM labels Sep 19, 2017
@eggrobin
Copy link
Member

The number of steps of the target prediction does not appear to be set correctly when changing that of the active vessel.

prediction_adaptive_step_parameters) const {
// If there is a target vessel, it is integrated with the same parameters as
// the given (current) vessel. This makes it possible to plot things like the
// closest approaches.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To plot the prediction of the current vessel, markers are just a special case.

@eggrobin eggrobin added the LGTM label Sep 21, 2017
@pleroy pleroy merged commit 6c7b951 into mockingbirdnest:master Sep 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants